How to skip nuget.config - #154039

All commit authors signed the Contributor License Agreement.

Documentation build overview

📚 cpython-previews | 🛠️ Build #33900211 | 📁 Comparing c572131 against main (c08c89a)

  🔍 Preview build  

This documentation doesn't relate to the issue you've linked.

I'm not totally opposed to having troubleshooting for Nuget configurations here, but it's not really our responsibility, so we should move it to the end of the section. It should also be written for casual human readers, not contributors, so the language needs to be expanded slightly and include a bit more context for when the error may occur.

We should also remove the reference to gh-114073 from the bug title and eventual commit message (this is our responsibility, not the PR author's), so that people don't confuse this section for build instructions in the future.

Oh you're right, I misunderstood what that issue was about. I thought it was for building software using a nuget-provided python executable. That issue helped me realize why nuget wasn't getting python for me.

To summarize my reading of the current instructions in that section, it is:

1. If you want a minimal executable, you can use nuget
2. To use it, download https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
3. Then run nuget.exe install python -ExcludeVersion -OutputDirectory .

For me, those minimal steps missed step 2.5 to run nuget.exe sources add -Name "nuget.org" -source "https://api.nuget.org/v3/index.json"

I didn't write my PR as a new step 2.5 in case there's other ways to install nuget which already come with sources pre-configured.

Yeah, I think in most cases Nuget's defaults will work, and it's only in some strange cases (most likely because something has modified Nuget's settings previously) where you need to restore the defaults.

As I said, putting it last in that section as a potential troubleshooting step is fine, but our main instructions shouldn't be interrupted by it (e.g. where it's written right now is an interruption).

As requested, I've moved text to end of the section and removed gh-114073 issue title link.

@zooba did you want me to create a different issue so it's not failing that 1 required check? No rush, I just want to confirm you're not waiting on me for anything.

Nah, it's a trivial docs update, we don't need an issue for it. Thanks!